Optimizing an operating system I/O operation that pertains to a specific program and file

ABSTRACT

An embodiment of the invention pertains to a method that includes an operating system, program components running on the operating system, and a file system associated with one or more files. Responsive to a write request sent from a specified program component to the operating system, in order to write specified data content to a given file, the method determines whether the write request meets a criterion, which is derived from the identity of at least one of the specified program component, and the given file. If the criterion is met, a message is immediately sent to release the specified program component from a wait state. Data portions of the specified data content are then selectively written to a storage buffer, and subsequently written from the buffer to the given file.

This application is a continuation of and claims the benefit of priorityto U.S. patent application Ser. No. 13/534,958, filed on Jun. 27, 2012and entitled “Optimizing an Operating System I/O Operation that Pertainsto a Specific Program and File”. The contents of which are herebyincorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention disclosed and claimed herein pertains to a method andapparatus for optimizing an input/output (I/O) operation of an operatingsystem. More particularly, the invention pertains to a method andapparatus of the above type, wherein optimization is achieved by usingthe identities of a specific file and program, or program component,which are related to or associated with the I/O operation.

2. Description of the Related Art

Application programs running on a computing platform often need to domany file I/O operations, such as writing data to a related file systemin a disk storage or the like, and reading data from the file system.Whether or not data is read from the file system, nearly all applicationprograms must write data to a file of the file system at some time. Forexample, applications generally need to log respective events to a fileon the disk. This typically involves APIs of the file system.

While file system APIs are not the same in all program languages, it isgenerally true that all APIs hand over read and write requests to theunderlying operating system. The operating system then carries out I/Ooperations that are respectively associated with or specified by therequests. More particularly, if an application program calls or sends anI/O request such as a write request to a given API, the API will deliverthe write request to the operating system. However, a problem in sucharrangements is that after the call, the API may block furtherprocessing activity of the caller application. The given API will returncontrol to the caller only after data content pertaining to the writerequest has been written to the disk. This problem can affect bothsynchronous and asynchronous I/O operations.

In synchronous file I/O, an application thread starts an I/O operationand then immediately enters a wait state, until the I/O request hascompleted and the thread is notified of the completion. In asynchronousfile I/O, an application thread calls an I/O request, and then continuesprocessing another job until the operating system kernel signals to thethread that the called I/O operation is complete. The thread theninterrupts its current job, and processes data pertaining to the I/Ooperation as necessary. Thus, application programs that write data todisk files generally are interrupted for a time which is directlyproportional to the amount of data that must be written to the disk.This occurs because calls to start write operations by using the filesystem APIs are in turn implemented by the underlying operating system.The operating system blocks the calling application until the writeoperation is completed.

SUMMARY

In embodiments of the invention, a layer of an operating systemintercepts I/O operations such as a write to a file, which is sent froman application or other program. Data content of an I/O operation thatis to be written is delivered to a buffer before being written to thefile, so that the time the program is interrupted by the I/O operationmay be significantly reduced. It may also be determined that it is notnecessary to write some or all of the data content to the file.

Embodiments of the invention can include a method, an apparatus, and acomputer program product. One embodiment pertains to a method in a dataprocessing system that includes an operating system, one or more programcomponents running on the operating system, and a file system associatedwith one or more files. In response to a given write request sent from aspecified program component to the operating system, in order to writespecified data content to a given file, the method determines whetherthe given write request meets a criterion, wherein the criterion isderived from the identity of at least one of the specified programcomponent, and the given file. Responsive to determining that the givenwrite request meets the criterion, a message is immediately sent torelease the specified program component from a wait state. The methodfurther includes selectively writing data portions of the specified datacontent to a storage buffer, and subsequently writing each data portionfrom the storage buffer to the given file.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating components for an embodimentof the invention.

FIG. 2 is a flow chart that shows steps of an algorithm for anembodiment of the invention.

FIG. 3 and FIG. 4 are schematic diagrams that each depicts componentsfor an embodiment of the invention.

FIG. 5 is a block diagram showing a computer or data processing systemthat may be used in implementing embodiments of the invention.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Referring to FIG. 1, there is shown a computer or data processing system100 that comprises an operating system 102, wherein operating system 102has a file system layer 104 and an API layer 106. System 100 furthercomprises a number of software programs or program components, such asapplication programs. These are shown in FIG. 1 as program components108 and 110, also referenced as components 1 and N, respectively, whereN is any reasonable number greater than 1. As used herein, the term“program component” means or refers to any software program or portionthereof, including, without limitation, application programs;application services such as operating system service programs; softwareprograms in the form of script language code, compiled code andinterpreted code; code implemented in hardware such as by a hardwarecomponent; and also any process or instance of any of the above.

FIG. 1 further shows API layer 106 provided with a write API 112, andwith a read API 114. Operating system 102 has an I/O manager layer 116,and an I/O router layer 120 that is provided with a bufferingcapability, represented as element 118. I/O router 120 is configured tofunction as a filtering component for write requests, by implementing analgorithm in accordance with an embodiment of the invention, asdescribed hereinafter in connection with FIG. 2. In these illustrativeexamples, I/O router 120 may be implemented by a program module that islocated in operating system 102, by a program module in a driver, suchas a file system driver, by a program module in an application program,or by any other mechanism suitable for providing program code to performthe operations of I/O router 120. For example, a file system may beinstalled to operate in conjunction with operating system 102. In thisexample, the installation of the file system may interact with I/Omanager layer 116 to configure a program module, such as a driver andother plug-in, located in the file system for use as I/O router layer120. As another example, an application program running in operatingsystem 102 may use application programming interfaces in I/O managerlayer 116 to configure a call back to a program module in theapplication program for use as I/O router layer 120. Operating system102 is further provided with a layer 122, which pertains collectively toother filter drivers included in operating system 102, if any, asdescribed hereinafter in further detail.

System 100 further includes a storage disk 124, such as a hard diskdrive or other hardware for storing data. Data is stored in disk 124 inclose association with file system 104.

Referring further to FIG. 1, there is shown a write request sent fromone of the program components, such as program 108, to operating system102. The write request is initially directed to write API 112, and isthen sent by I/O manager 116 to I/O router 120. Upon receipt, I/O router120 makes one or more decisions in regard to the write request and thedata content associated with the write request, as describedhereinafter. One of the decisions may be that the requested writeoperation should be treated as though it was then completed. In thisevent, a control return message is immediately sent back to theapplication or other program that sent the write request, such asmessage 126 sent to program 108. Upon receiving this message, the callerprogram is no longer blocked by the operating system, and may exit froma wait state.

In operating system 102 of FIG. 1, file system layer 104 is configuredto add functionality to each of the layers 116, 120 and 122, in order toenable each layer to carry out its respective tasks. Functionality isadded by implementing program components to use in each of these layers.

FIG. 1 further shows the disk 124 partitioned to include a FileAllocation Table (FAT) component 126, and a New Technology File System(NTFS) component 128. File system 104 is provided with correspondingcomponents 130 and 132.

Referring to FIG. 2, there are shown steps for an algorithm or otherprocedure for implementing an embodiment of the invention. The algorithmmay be implemented by I/O router 120 of FIG. 1, when a write request isreceived by I/O router 120. However, the invention is not limitedthereto. In the embodiment of FIG. 2, the algorithm starts when a writerequest is received by the I/O router 120 or other implementingcomponent. It is understood that a write request will be sent from aparticular program or program component, such as application program108, and will indicate that specified data content is to be written to aparticular file of disk 124.

In accordance with embodiments of the invention, it has been recognizedthat the program source of a write request, the file to which the datacontent of a write request is directed, or both the program source andthe file, can be very significant in determining how successive writerequests are to be handled. In view of this, step 202 requiresidentifying or defining both the program component and the fileassociated with a received write request. Usefully, the identity of thefile is included with the write request, and can be acquired therefrom.The program component may usefully be identified from the command thatwas used to start the program component. Alternatively, other file andprogram identifiers may be derived from the write request.

Step 204 of the algorithm of FIG. 2 requires determining whether theprogram component and/or the file of a received write request matches apattern, or meets a criterion, which is provided or specified by a setof rules. FIG. 2 shows a set of rules 206, which is furnished to step204 for use thereby. Illustrative examples of rules which could beincluded in a set of rules 206 are set forth hereinafter as RuleExamples 1-4.

Both Text Matching and Regular Expressions can be used in implementingrules for evaluating write requests. With Text Matching, a rule can becreated which intercepts a write request, and thus selects it forfurther processing in accordance with the algorithm of FIG. 2, if thename of the file exactly matches a text provided by a user. An exampleof this is as follows:

Rule Example 1

If filename equals “C:/Program Files/WebServer/logs/activity.log” thenrun policies else redirect to operating system

Rule Example 2

An example of the use of Regular Expressions to match files could bethat the Regular Expression will match any file that has an extensionlog. As an illustration, this expression would match:

“C:/Program Files/WebServer/logs/activity.log” or“/opt/WebServer/logs/activity.log”.

Stated more generally, this rule would be as follows:

If filename matches “.*\.log” then run policies else redirect tooperating system

The above two examples match the file that is being written to, asindicated by the write request. As another option, a rule can be basedon the program or program component that is writing to a file, and thusprovides the write request. In an operating system, a program istypically defined or identified by a command that was issued to startit, or by a. It would generally be more useful to use the command toidentify the program component, as stated above, since the process idcan change each time the program runs. An example of a rule 206 whichidentifies the program that is writing to a file would be as follows:

Rule Example 3

If command equals “/root/WebServer/bin/startWebServer.sh” then runpolicies else redirect to operating system

The above rule will intercept any file writing that is done by theprogram “/root/WebServer/bin/startWebServer.sh”. However, for somesituations it may not be a good idea to intercept every write requestfrom this program. Accordingly, a rule may be used that includes boththe identities of the program and the file being written to. An exampleof this rule is as follows:

Rule Example 4

If command equals “/root/WebServer/bin/startWebServer.sh” and filenameequals “C:/Program Files/WebServer/logs/activity.log” then run policieselse redirect to operating system

The above exemplary rules could generally be in any language, based on agiven implementation. By creating a set of such rules, a set of detailedconditions or criteria are provided which are used by I/O router 120 todecide whether it needs to intercept a given write request, or hand itback to the operating system. Thus, referring further to FIG. 2, if itis determined at step 204 that neither the program component or the fileassociated with a write request matches a criterion or pattern of a setof rules, as described above, the write request is not intercepted byI/O router 120. Instead, the write request is redirected back to theregular flow or process of operating system 102, and the algorithm ofFIG. 2 ends.

Conversely, if the program component and/or file of the write requestdoes match a pattern or criterion of a set of rules, the write requestis intercepted and the algorithm proceeds to step 210. At this step, oneor more policies of a set of polices 212 are applied to the writerequest and to data content associated with the request. Also, as shownat step 214, a message is sent to return control to the write requestcaller, such as the application program or other program component thatcalled the write request. Such caller is thereby released from any waitstate it may have been in, and can immediately return to processingactivity, while the write request is being handled further.

After a write request has been intercepted, a wide range of actions canbe taken at step 210, as determined by respective policies 212. Theterms “Condition”, “Action” and “Content” are associated with examplesof policies 212, which are set forth below. These terms are defined asfollows:

-   -   Condition—A condition is (similar to in a rule) any check that        is run and results in a True or False    -   Action—An action is a task that must be performed and in this        case based on the result of a condition.    -   Content—Content refers to the actual data being written to a        file

In a policy 212, the conditions could be significantly more complex thanfor rules 206. A policy could decide to take an Action based on theContent of the write request, or mathematical functions or even on thecurrent time of day, by way of example. An example of a policy 212 is asfollows:

Policy Example 1

A user could choose to ignore or modify the Content being written. In anexample, a program is trying to write the following lines to a file(which could typically appear in a WebServer log file):

[13/10/11 8:36:17:144 CEST] DEBUG[EncodingPrestationsSDO:BUDO23046:808346] SELECT RRN(p) [13/10/118:36:17:168 CEST] DEBUG [EncodingPrestationsSDO:BUDO23046:808346] SQLDone in ms 24 size 3 [13/10/11 8:36:17:272 CEST] DEBUG[EncodingPrestationsSDO:LEONA:808326] SQL Done in ms 213 size 55[13/10/11 8:36:17:355 CEST] DEBUG [CarteSocialeBean:POSKI:808342]PAT002AR BasicBean.handleRPGErrorParams: No OUTRETUPD --> skipping[13/10/11 8:36:18:055 CEST] DEBUG [EncodingPrestationsSDO:BONOMO:808387]SELECT RRN(p) [13/10/11 8:36:18:147 CEST] INFO [AS400ConnectionFactory:]!!! AS400ConnectionFactory.getConnection - NEW as400 connection foruser:WASY23260 for sessionID:k51QAGSZXRtkKfJqU-0CZyG [13/10/118:36:18:157 CEST] ERROR [LoginBean:] !!! LoginBean.login - when errordestroy this connection for sessionID:k51QAGSZXRtkKfJqU-0CZyG [13/10/118:36:18:157 CEST] INFO [WishConnectionFactory:] destroySession - closeAS400 and JDBC connection for sessionID:k51QAGSZXRtkKfJqU-0CZyGWASY23260 [13/10/11 8:36:18:255 CEST] ERROR [CMD020MR:]com.ibm.as400.access.AS400SecurityException: Password is incorrect.The user could decide that any line that contains the word DEBUG can beignored, because this is useful only to the programmer of theapplication, and does not help the System Administrator on a liverunning deployment. In this case, the user doesn't have a specificCondition to check, but only wants to modify the content. Thus, thepolicy would simply have an action to take on the Content, as follows:

policy { removeDebugData(Content) };Once this action is taken, the final write to the file would onlycontain

[13/10/11 8:36:18:147 CEST] INFO [AS400ConnectionFactory:] !!!AS400ConnectionFactory.getConnection - NEW as400 connection foruser:WASY23260 for sessionID:k51QAGSZXRtkKfJqU-0CZyG [13/10/118:36:18:157 CEST] ERROR [LoginBean:] !!! LoginBean.login - when errordestroy this connection for sessionID:k51QAGSZXRtkKfJqU-0CZyG [13/10/118:36:18:157 CEST] INFO [WishConnectionFactory:] destroySession - closeAS400 and JDBC connection for sessionID:k51QAGSZXRtkKfJqU-0CZyGWASY23260 [13/10/11 8:36:18:255 CEST] ERROR [CMD020MR:]com.ibm.as400.access.AS400SecurityException: Password is incorrect.

Applying the above policy to the data content of a write request assistsin ensuring that disk space is not used up by data that is not needed.

A further example of a policy 212 is as follows:

Policy Example 2

It is required to notify a System Administrator when a WebServer logs avery specific error message, “ERROR Server has crashed”. During workinghours, the administrator must be sent an email and at other times an SMSmessage must be sent to his mobile phone. Also, a rule has already beenrun to check that the filename and the command match C:/ProgramFiles/WebServer/logs/activity.log” and“/root/WebServer/bin/startWebServer.sh”, and it has been determined thata notification as required above must be made to the SystemAdministrator. A policy to accomplish this could be as follows:

policy { If Content contains “ERROR Server has crashed” then { IfduringWorkingHours(currentTime) then sendEmail(Content) elsesendSMSMessage(Content) } };To paraphrase this policy, first the Content is checked for a specificset of words. If these are there, then the policy checks if the currenttime is during working hours. If it is working hours, then an email issent containing the Content that was to be written to a file, andotherwise the same is sent via an SMS message.

Referring further to FIG. 2, after any pertinent policies have beenapplied to a write request and its associated data content, step 216determines whether any portions of the data content are to be written tothe file specified by the write request. It is anticipated thatapplication of some policies 212 in fact will require that none of thedata content is to be written to the file. In this case, the algorithmof FIG. 2 will end.

If it is determined at step 216 that some or all portions of the datacontent are to be written to the file, each of such data portions iswritten to a storage buffer in accordance with step 218. The buffercould, for example be a cache associated with the memory of system 100.

At step 220, each data portion written to the storage buffer issubsequently written to the file specified by the write request, such asa file on disk 124. This action is taken in accordance with any policiesthat apply. For example, a policy may require that data in the buffer isto be written to the disk when the buffer size exceeds 20 kb, or data isto be written to the disk at regular intervals of 5 minutes or the like.

At step 222, it is necessary to determine whether or not any furtheraction is required. If not, the algorithm ends. Otherwise, the algorithmproceeds to step 224 to take the necessary action. One example of suchfurther action would be the need to send an email or an SMS message tothe system administrator, as required by Policy Example 2, describedabove.

By means of the algorithm of FIG. 2, the set of rules can be used toquickly decide if a given write request should be intercepted or not. Ifthe write request is intercepted, a wide range of actions can then betaken in regard to the write request and its content.

Referring to FIG. 3, there is shown an embodiment of the invention,wherein an I/O manager 302 of an operating system is similar oridentical to I/O manager 116 of FIG. 1. Various I/O requests come to I/Omanager 302, such as a write request shown as an input thereto. I/Omanager 116 issues I/O Request Packets (IRPs) and fast I/O requests to aFile System Driver (FSD), which may comprise one or more filter drivercomponents. In the embodiment of FIG. 3, a filter driver 304, which isconfigured to carry out respective functions of I/O router 120 asdescribed above, is positioned between I/O manager 116 and filter drivercomponents 306 and 308 of the FSD.

Filter driver 304 performs a filtering process on received writerequests, as described above in connection with FIG. 2. Some of the datacontent of write requests is routed to a buffer by filter driver 304.This is carried out in the embodiment of FIG. 3 by directing the writerequests to a cache manager 310. Filter driver 304 may also determinethat some or all of the data content of a write request should not bewritten to disk file. Filter driver 304 may determine further that areceived write request should simply flow through to filter drivercomponents 306 and 308 of the FSD, for processing thereby.

Component 306 pertains to replication. Component 308 is directed togeneric filter drivers associated with different functions, includingquotas and encryption, but is not limited thereto. The FSD of FIG. 3 candeliver data to disk 312 of a File Allocation Table (FAT) 314, to a disk316 of a New Technology File System (NTFS) 318, or to a securecommunication network 320 such as an RDR network.

FIG. 4 shows an embodiment of the invention which is similar to theembodiment of FIG. 3, except that write requests from I/O manager 302are delivered to a virtual file system (VFS) 402 instead of an FSD. Thewrite requests are then sent to a file system driver 404, which carriesout the respective functions of I/O router 120 as described above.

FIG. 5 depicts a diagram of a data processing system in accordance withan illustrative embodiment. Data processing system 500 is an example ofa computer, which may be used to implement one or more components ofembodiments of the invention, and in which computer usable program codeor instructions implementing the processes may be located for theillustrative embodiments. In this illustrative example, data processingsystem 500 includes communications fabric 502, which providescommunications between processor unit 504, memory 506, persistentstorage 508, communications unit 510, input/output (I/O) unit 512, anddisplay 514.

Processor unit 504 serves to execute instructions for software that maybe loaded into memory 506. Processor unit 504 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 504 may beimplemented using one or more heterogeneous processor systems, in whicha main processor is present with secondary processors on a single chip.As another illustrative example, processor unit 504 may be a symmetricmulti-processor system containing multiple processors of the same type.

Memory 506 and persistent storage 508 are examples of storage devices516. A storage device is any piece of hardware that is capable ofstoring information, such as, for example, without limitation, data,program code in functional form, and/or other suitable informationeither on a temporary basis and/or a permanent basis. Memory 506, inthese examples, may be, for example, a random access memory, or anyother suitable volatile or non-volatile storage device. Persistentstorage 508 may take various forms, depending on the particularimplementation. For example, persistent storage 508 may contain one ormore components or devices. For example, persistent storage 508 may be ahard drive, a flash memory, a rewritable optical disk, a rewritablemagnetic tape, or some combination of the above. The media used bypersistent storage 508 may be removable. For example, a removable harddrive may be used for persistent storage 508.

Communications unit 510, in these examples, provides for communicationwith other data processing systems or devices. In these examples,communications unit 510 is a network interface card. Communications unit510 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 512 allows for the input and output of data with otherdevices that may be connected to data processing system 500. Forexample, input/output unit 512 may provide a connection for user inputthrough a keyboard, a mouse, and/or some other suitable input device.Further, input/output unit 512 may send output to a printer. Display 514provides a mechanism to display information to a user.

Instructions for the operating system, applications, and/or programs maybe located in storage devices 516, which are in communication withprocessor unit 504 through communications fabric 502. In theseillustrative examples, the instructions are in a functional form onpersistent storage 508. These instructions may be loaded into memory 506for execution by processor unit 504. The processes of the differentembodiments may be performed by processor unit 504 using computerimplemented instructions, which may be located in a memory, such asmemory 506.

These instructions are referred to as program code, computer usableprogram code, or computer readable program code that may be read andexecuted by a processor in processor unit 504. The program code, in thedifferent embodiments, may be embodied on different physical or computerreadable storage media, such as memory 506 or persistent storage 508.

Program code 518 is located in a functional form on computer readablemedia 520 that is selectively removable and may be loaded onto ortransferred to data processing system 500 for execution by processorunit 504. Program code 518 and computer readable media 520 form computerprogram product 522. In one example, computer readable media 520 may becomputer readable storage media 524 or computer readable signal media526. Computer readable storage media 524 may include, for example, anoptical or magnetic disc that is inserted or placed into a drive orother device that is part of persistent storage 508 for transfer onto astorage device, such as a hard drive, that is part of persistent storage508. Computer readable storage media 524 also may take the form of apersistent storage, such as a hard drive, a thumb drive, or a flashmemory that is connected to data processing system 500. In someinstances, computer readable storage media 524 may not be removable fromdata processing system 500.

Alternatively, program code 518 may be transferred to data processingsystem 500 using computer readable signal media 526. Computer readablesignal media 526 may be, for example, a propagated data signalcontaining program code 518. For example, computer readable signal media526 may be an electromagnetic signal, an optical signal, and/or anyother suitable type of signal. These signals may be transmitted overcommunications links, such as wireless communication links, an opticalfiber cable, a coaxial cable, a wire, and/or any other suitable type ofcommunications link. In other words, the communications link and/or theconnection may be physical or wireless in the illustrative examples. Thecomputer readable media also may take the form of non-tangible media,such as communications links or wireless transmissions containing theprogram code.

In some illustrative embodiments, program code 518 may be downloadedover a network to persistent storage 508 from another device or dataprocessing system through computer readable signal media 526 for usewithin data processing system 500. For instance, program code stored ina computer readable storage media in a server data processing system maybe downloaded over a network from the server to data processing system500. The data processing system providing program code 518 may be aserver computer, a client computer, or some other device capable ofstoring and transmitting program code 518.

The different components illustrated for data processing system 500 arenot meant to provide physical or architectural limitations to the mannerin which different embodiments may be implemented. The differentillustrative embodiments may be implemented in a data processing systemincluding components in addition to and/or in place of those illustratedfor data processing system 500. Other components shown in FIG. 5 can bevaried from the illustrative examples shown. The different embodimentsmay be implemented using any hardware device or system capable ofexecuting program code. As one example, data processing system 500 mayinclude organic components integrated with inorganic components and/ormay be comprised entirely of organic components excluding a human being.For example, a storage device may be comprised of an organicsemiconductor.

As another example, a storage device in data processing system 500 isany hardware apparatus that may store data. Memory 506, persistentstorage 508, and computer readable media 520 are examples of storagedevices in a tangible form.

In another example, a bus system may be used to implement communicationsfabric 502 and may be comprised of one or more buses, such as a systembus or an input/output bus. Of course, the bus system may be implementedusing any suitable type of architecture that provides for a transfer ofdata between different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, memory 506 or a cache such asfound in an interface and memory controller hub that may be present incommunications fabric 502.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiment. The terminology used herein was chosen to best explain theprinciples of the embodiment, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed here.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. In a data processing system that includes anoperating system, one or more program components running on theoperating system, and a file system associated with one or more files, acomputer program product executable in a computer recordable storagemedium comprising: instructions responsive to a given write request sentfrom a specified program component to the operating system, in order towrite specified data content to a given file, for determining whetherthe given write request meets a criterion derived from the identity ofat least one of the specified program component and the given file;instructions responsive to determining that the given write requestmeets said criterion, for immediately sending a message to release thespecified program component from a wait state and applying one or morepolicies to the specified data content, in order to determine whetherany portion of the specified data content needs to be written to thegiven file, and if so, selecting each such data portion to be written tothe given file; instructions for selectively writing data portions ofthe specified data content to a storage buffer based on the one or morepolicies; and instructions for subsequently writing each data portion ofthe data portions in the storage buffer to the given file.
 2. Thecomputer program product of claim 1, wherein: the specified programcomponent is in a wait state prior to determining that the given writerequest meets the criterion, and the specified program is released fromthe wait state before any of the specified data content is written tothe given file.
 3. The computer program product of claim 1, wherein: itis determined by applying one of said policies to the specified datacontent that a specified portion of the specified data content should bewritten to the given file, wherein said specified portion is less thanall of the specified data content.
 4. The computer program product ofclaim 1, wherein: it is determined by applying one of said policies tothe specified data content that none of the specified data contentshould be written to the given file.
 5. The computer program product ofclaim 1, wherein: the operating system has a specified process forhandling write requests, and responsive to determining that the givenwrite request does not meet said criterion, the given write request isdirected or redirected, selectively, to said specified handling processof the operating system.
 6. The computer program product of claim 5,wherein: the specified process for handling write requests of theoperating system is an instance of a program module configured in theoperating system to intercept write requests received by the operatingsystem.
 7. The computer program product of claim 1, wherein: saidcriterion is met if the given file of the given write request matches apredetermined file, or if the specified program component of the givenwrite request matches a predetermined program component, wherein thegiven file matching the predetermined file is determined using a regularexpression rule that specifies a logical expression that the given fileconforms to, and wherein the predetermined program component isidentified from a command used to start the program component.
 8. Thecomputer program product of claim 1, wherein: said criterion is met ifboth the given file of the given write request matches a predeterminedfile, and the specified program component thereof matches apredetermined program component.
 9. The computer program product ofclaim 1, wherein: responsive to applying one or more of said policies tothe specified data content, it is determined that further action needsto be taken, in addition to writing any selected data portion to thestorage buffer or to the given file.
 10. The computer program product ofclaim 9, wherein: said further action comprises sending a specifiedmessage to a system administrator.
 11. In a data processing system thatincludes an operating system, one or more program components running onthe operating system, and a file system associated with one or morefiles, an apparatus comprising: processing means, responsive to a givenwrite request sent from a specified program component to the operatingsystem, in order to write specified data content to a given file, fordetermining whether the given write request meets a criterion, whereinsaid criterion is derived from the identity of at least one of thespecified program component and the given file; processing means,responsive to determining that the given write request meets saidcriterion, for immediately sending a message to release the specifiedprogram component from a wait state and applying one or more policies tothe specified data content, in order to determine whether any portion ofthe specified data content needs to be written to the given file, and ifso, selecting each such data portion to be written to the given file;processing means for selectively writing data portions of the specifieddata content to a storage buffer based on the one or more policies; andprocessing means for subsequently writing each data portion of the dataportions in the storage buffer to the given file.
 12. The apparatus ofclaim 11, wherein: the specified program component is in a wait stateprior to determining that the given write request meets the criterion,and the specified program is released from the wait state before any ofthe specified data content is written to the given file.
 13. Theapparatus of claim 11, wherein: it is determined by applying one of saidpolicies to the specified data content that a specified portion of thespecified data content should be written to the given file, wherein saidspecified portion is less than all of the specified data content. 14.The apparatus of claim 11, wherein: it is determined by applying one ofsaid policies to the specified data content that none of the specifieddata content should be written to the given file.
 15. The apparatus ofclaim 11, wherein: the operating system has a specified process forhandling write requests, and responsive to determining that the givenwrite request does not meet said criterion, the given write request isdirected or redirected, selectively, to said specified handling processof the operating system.
 16. The apparatus of claim 15, wherein: thespecified process for handling write requests of the operating system isan instance of a program module configured in the operating system tointercept write requests received by the operating system.
 17. Theapparatus of claim 11, wherein: said criterion is met if the given fileof the given write request matches a predetermined file, or if thespecified program component of the given write request matches apredetermined program component, wherein the given file matching thepredetermined file is determined using a regular expression rule thatspecifies a logical expression that the given file conforms to, andwherein the predetermined program component is identified from a commandused to start the program component.
 18. The apparatus of claim 11,wherein: said criterion is met if both the given file of the given writerequest matches a predetermined file, and the specified programcomponent thereof matches a predetermined program component.
 19. Thecomputer program product of claim 8, wherein: the given file matchingthe predetermined file is determined using a regular expression rulethat specifies a logical expression that the given file conforms to, andwherein the predetermined program component is identified from a commandused to start the program component.
 20. The apparatus of claim 18,wherein: the given file matching the predetermined file is determinedusing a regular expression rule that specifies a logical expression thatthe given file conforms to, and wherein the predetermined programcomponent is identified from a command used to start the programcomponent.